Vehicle identification and device communication through directional wireless signaling

ABSTRACT

There are provided systems and methods for vehicle identification and device communication through directional wireless signaling. A user&#39;s device may include a directional wireless transceiver that may be used to provide wireless signaling in a specific target direction. The user may direct the device at a particular vehicle, where the vehicle may has a transceiver located within or attached to the vehicle that responds to the particular wireless signaling. The vehicle&#39;s transceiver may respond to the device of the user with a unique identifier that allows for communication with the vehicle&#39;s operator. The unique identifier may therefore allow for message content to be sent directly to a device for the vehicle&#39;s operator, or may allow for a service provider to process the message. Additionally, the vehicle&#39;s operator may establish privacy settings for communications, which may be utilized to determine whether the message content will be provided to the device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/323,712, filed May 18, 2021, which is a continuation of U.S. patentapplication Ser. No. 16/019,188, filed on Jun. 26, 2018, issued as U.S.Pat. No. 11,012,401, all of which are incorporated by reference in theirentirety.

TECHNICAL FIELD

The present application generally relates to directional wirelesssignaling and vehicle identification and more specifically to providingidentification of a vehicle and a device associated with the vehicle fordirect communication using a wireless communication component thatprovides directional signaling.

BACKGROUND

When utilizing vehicles, operators may be unaware of particular vehicleconditions that introduce safety hazards or financial consequences. Forexample, a driver of a car may be unaware that their gas tank is open orthat a panel is loose, which may harm the vehicle and/or other carsoperating near the vehicle. At other times, a car may be parked but theparking spot may be in an unauthorized area or where a parking meter hasexpired. Other vehicle operators may see the hazard, but may be unableto directly communicate with the driver of the vehicle. The otheroperators may attempt to get the attention of the driver by honking ahorn or flashing lights at the vehicle, but this may introduceadditional hazards and divert the attention of the driver and otherdrivers. At other times, the vehicle may be unattended and the vehicle'sowner may not be in close enough proximity to resolve the issue.Alerting a police service or other authority may allow for tracking ofthe vehicle, but may not immediate assist the driver. Thus, thepotential issue may be unresolved and cause harm.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system suitable forimplementing the processes described herein, according to an embodiment;

FIG. 2A is an exemplary real-world environment for directional wirelesscommunication for vehicle identification and device communication,according to an embodiment;

FIG. 2B is an exemplary real-world environment for vehicleidentification and device communication where multiple vehicles areoperating in close proximity, according to an embodiment;

FIG. 3A is a flowchart of an exemplary process executed by a serviceprovider for vehicle identification and device communication, accordingto an embodiment;

FIG. 3B is a flowchart of an exemplary process executed by a device forvehicle identification and device communication, according to anembodiment;

FIG. 4 is a flowchart of an exemplary process for vehicle identificationand device communication through directional wireless signaling,according to an embodiment; and

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 , according to an embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Provided are methods utilized for vehicle identification and devicecommunication through directional wireless signaling. Systems suitablefor practicing methods of the present disclosure are also provided.

An observer of a vehicle may notice an issue with the vehicle and maywish to report the issue to the operator of the vehicle or otherauthority. The observer may utilize a first communication device, suchas a mobile smart phone, to determine an identifier for the vehicle, forexample, by using directional wireless communications targeting thevehicle and capturing additional data for the vehicle if necessary. Thedirectional wireless communications may allow the first device toretrieve an identifier for the vehicle from a communication componentassociated with the vehicle, such as a vehicle's on-board computingdevice, a wireless transceiver beacon attached to or included with thevehicle, and/or another communication device within the vehicle (e.g., amobile smart phone of a driver or passenger in the vehicle). Theadditional data received by a directional transceiver of the firstdevice may be utilized to uniquely identify the particular vehiclethrough data analysis by the first device and/or a service provider.After retrieving the unique identifier for the vehicle, the observer'sfirst device may be used to determine an identifier of a person orentity associated with the vehicle and generate a communication to asecond device associated with the person or entity (generally referredto herein as an operator) of the vehicle. This communication may includecaptured data by the first device, as well as a message or othernotification. Privacy settings by the vehicle's operator may determinewhether the vehicle's unique identifier may identify the second deviceand allow for direct communications, or whether the unique identifiermay keep the operator as anonymous and/or cause a service provider toprocess the message data to determine whether the message is transmittedto the second device. Additionally, the observer's first device may beused to process a transaction to assist the vehicle's operator, such asa payment for parking, where reimbursement may be requested from thesecond device and/or processed using an account of the second devicewith the service provider.

In order to provide wireless signaling that may be used to identify avehicle and therefore a device associated with the vehicle so that anoperator of the vehicle may be notified of vehicle issues or hazards, afirst user's device may include a wireless transceiver and additionaldata detection and recording components. The first user may correspondto another vehicle operator, bystander, or other person that observes avehicle and notices an issue with vehicle operation, use, or storage,such as a financial issue due to insufficient fees paid by the vehicleowner or a hazard during operation of the vehicle. The first user'sdevice may therefore include the wireless transceiver component, such asa communication module, that may communicate with other nearby devicesthrough wireless signaling when the other devices are within a wirelessproximity range of the first user's device (e.g., a radius or otherdistance from the first user's device). The wireless transceiver mayfurther include directional wireless signaling capabilities, which maybe used to point a specific part or component of the first user's devicetoward a direction and direct signaling in that direction. Thus, thewireless transceiver may be capable of being directed in a specificdirection for wireless communications with devices in that direction(e.g., within the line-of-sight). This signaling may be done throughWiFi, Bluetooth, Bluetooth Low Energy (BLE), infrared, or other types ofsignaling that provide directional communication capabilities.

The first user's device may further include additional components thatmay capture information about the vehicle that the first user istargeting for communication, such as a GPS locator or other locationdetection component that may determine a geo-location of the deviceand/or a route traveled by the device. The device may also include acompass functionality or other application or instrument for navigation,including gyroscopes and/or accelerometers. The first user's device mayutilize one or more additional components and sensors, such as a cameraor other visual or optical capture device, to capture data of thevehicle at the location and identify the vehicle. Additionally, thedevice may include a microphone and audio recording process, as well asan audio processing feature to process voice input, such as avoice-to-text process. The first user's device may also include atransceiver that may allow for wireless communications with one or moreother devices or servers, including over cellular communications (e.g.,3G, 4G, 4G Long Term Evolution (LTE), 5G, other 3^(rd) GenerationPartnership Project (3GPP)-based cellular communications), or othertypes of wireless communications.

The vehicle may include a wireless transceiver unit that may store aunique identifier or identification token for the vehicle that allowsother devices to uniquely identify the vehicle for communications. Thetoken may further be generated for the vehicle specifically and so thatan identity of the vehicle's operator (e.g., a second user associatedwith the vehicle) remains anonymous (i.e., the token does not permitidentification of the vehicle's operator and/or the operator's devicedirectly) if so desired by the user. For example, the token may includea randomly generated identifier or obscured identifier for the seconduser associated with the vehicle that does not permit direct contactwith the second user. The token may be generated when the second useropts-in to a service provided by a service provider that allows forcommunication by other observers of the vehicle (e.g., the first user)for reporting of vehicle issues. When the second user opts-in to theservice, the service provider may allow the second user to establishprivacy preferences, such as whom, when, or why the second user may becontacted regarding the second user's vehicle. Thus, the token may begenerated based on such preferences. The token may be stored on a devicefor the second user, such as a mobile computing device, or may be storedon a device for the vehicle, such as a console or on-board computingdevice, vehicle wireless locking component, vehicle communicationmodule, or other device. Additionally, a wireless transceiver may beadded to or mounted on the vehicle, which may store the token. Thus, thevehicle may include a wireless transceiver having an antenna tocommunicate with the first user's device, and used to transmit the tokento the first user's device.

The first user's device may transmit a signal through wirelesscommunications to the vehicle's device, which may be directionallytransmitted in a certain direction or location for receipt by thevehicle's device. When establishing a connection, the first user'sdevice may emit a communication signal, which may include a query orrequest for the data token from the vehicle's device. The receivingdevice may execute specialized hardware and/or software to respond tothe wireless communications, for example, through a communicationmodule. This may be done passively utilizing an “always-on” type signal,or may be performed actively by an application of the device. When thevehicle's device detects the signal, the device may respond with thetoken. Additionally, the devices may establish a connection, where theconnection may further enable the device to communicate additionalinformation and/or determine distances through a received signalstrength indications (RSSI) (e.g., Bluetooth RSSI), and/or exchangeadditional information. The token may keep the second user anonymous toprevent identification by the first user's device, and therefore doesnot directly identify the second user or the second user's device (e.g.,the vehicle's device).

Where directional wireless communications are not used to detectmultiple vehicle devices and associated tokens, additional data may alsobe used to determine a particular vehicle targeted by the first user forcommunication and notification of a vehicle issue. In order to identifythe particular vehicle, the first user's device may capture additionaldata using a data detection component. For example, an image of thevehicle may be captured, a location of the first user's device may bedetermined, an orientation of the first user's device may be determined(e.g., using a compass, accelerometer, and/or gyroscope), and/or voiceinput by the first user may be recorded. Such data may be processed todetermine the specific vehicle, for example, through image recognitionof the vehicle with voice-to-text identification of the vehicle (e.g.,if the user requests to identify the “white car” or the “pickup truck”).Additionally, a location of the device, direction the device isoriented, and/or image may be compared to all the tokens received toidentify the particular vehicle (e.g., by determining that the device ispointed at a “truck” where three received tokens include only one for atruck). The first user's device may include an application withprocessing capabilities to identify the vehicle, or may detect the dataand transmit the data to a service provider for processing. Thus, if thevehicle includes a color, shape, light, license plate, or visibleQR/bar-code, the first user's device and/or service provider mayidentify the vehicle through such identifying characteristics, opticalrecognition, voice data processing, and location/orientation of thedevice. Such data may be used to hone in on the specific vehicle andidentify that vehicle's token. Where the first user's devicecommunicates locally with a vehicle's communication component usingcommunications (e.g., WiFi, Bluetooth, or BLE), the first user's devicemay utilize RSSI, geo-location information, camera data, or other datain the signals received over the communications to determine thespecific vehicle.

In various embodiments, a self-driving vehicle may also capture data ofa nearby vehicle that is used to determine identification of the nearbyvehicle and/or an issue with the nearby vehicle. Self-driving vehiclesmay be equipped with various sensors, including cameras and otheroptical detection and recognition components, distance sensors,speedometers or other acceleration/velocity detection components, andother sensors that may assist in operating a vehicle without or withminimal interaction by a user. These components may also be used todetect issues with other nearby vehicles, including operational issues(e.g., a flat tire, open gas tank, or other issue that may affectoperation of the vehicle). The sensors may also be used to determineissues with use of the vehicle, including speed (e.g., driving too fastor slow), swerving or driving unsafely, operating in the wrong lane orside of the road, etc. Moreover, the self-driving vehicle may alsodetect issues with vehicles that are not in operation, including expiredparking for parked vehicles or other issues that may affected a parkedvehicle. Using this information, the self-driving vehicle may utilizewireless communications and/or vehicle sensors to determine an identityof the problematic nearby vehicle (e.g., the white sedan, black Toyota®,or green Camry®), and may alert the operator or owner of theself-driving vehicle of the issue and the identification of theproblematic vehicle. For example, the self-driving vehicle may present amessage on a display and/or an audio output that includes identificationof the vehicle at issue and the issue (e.g., “The white sedan ahead hasa flat tire,” and additional options or advice including “Proceed withcaution!” or “Would you like to alert the white sedan of the flattire?”). The self-driving vehicle may then allow the operator/owner tocontact the problematic vehicle, as discussed herein.

After receiving the identifier for the vehicle, the first user's devicemay be able to communicate with the device associated with the seconduser for the vehicle, (e.g., the vehicle's console, on-board, orsmart-car device, or a computer device associated with the vehicle'soperator, such as a mobile phone). Since the second user may wish toremain anonymous to communications from other users that are associatedwith the vehicle, the token may prevent identification directly of thesecond user, such as a phone number, name, or messaging identifier.Instead, the token may be utilized by an application of the first user'sdevice and/or a service provider to direct communications to the seconduser's device while keeping the second user anonymous, for example, bypreventing identification of the second user to the first user. Theapplication of the first user's device may obscure a name and identifierof the second user but allow communication through the token, or aservice provider may utilize the token to route communications.Additionally, communications from the first user may remain anonymous tothe second user so that the first user's name or device identifier isalso hidden from viewing by the second user.

A message from the first user may then be sent to the second user'sdevice utilizing the token. The message may include message content,such as text that identifies the issue. The text may be entered througha voice-to-text process or may be directly input. The message may alsoinclude other notification data that is captured by the first user'sdevice, such as an image, location, time, or other contextualinformation that may assist the second user in identifying and resolvingthe issue. The message may be transmitted based on the privacypreferences and settings of the second user. For example, the seconduser may only allow emergency messaging that identifies a hazardouscondition, or may allow more relaxed standards for messaging includingif a meter is about to expire. Thus, the message data may be processedby the first user's device and/or the service provider to determinemessage content. In certain embodiments, the first user may be requiredto select one or more fields or subjects for the message utilizing aninterface of the application transmitting the message, which may be usedto determine the message content. In certain embodiments, the messagemay also or instead be transmitted to the service provider or anauthority entity for processing, for example, in the case of unsafedriving, breaking of laws, inebriated/drunk driving concerns, or otherpotential driver-based issues of the vehicle that may require anotherentity to intervene.

The first user's device and/or the service provider may also communicatedirectly with the vehicle's device where the vehicle's device mayprovide system monitoring, such as an on-board computing device orsmart-car device. This may allow the device/service provider todetermine whether the issue has been resolved prior to transmitting themessage. The first user's device may also be used to process atransaction on behalf of the second user for the vehicle using thevehicle token and/or a nearby device or networked system. For example,if the vehicle is parked in an area where their parking fee or meter isset to expire, the first user may provide a payment on behalf of thesecond user for the vehicle. The service provider system may process thetransaction, and may request reimbursement from the second user or maydirectly withdraw the funds from an account of the second user. Theservice provider may process transaction data and available vehicle datacaptured for the vehicle in order to ensure that a payment was required,and may provide a reimbursement process for the first user afterproviding the payment.

The service provider may also monitor message content to prevent thetransmission of unwanted messages, such as spam messages that do notcontain relevant vehicle information and/or abusive messages by users.The service provider may utilize text keyword analysis and/or other dataprocessing to determine the message content and whether the messageviolates terms that the users agree to when opting in to the serviceprovider's messaging service. Additionally, the service provider mayprovide a reporting service, which may allow the second user to reportthe first user, and vice versa, for harassing or unwanted messaging. Thereporting service may be used during future message content processingto determine whether the first or second user may message another user,and may place restrictions, blacklists, or bans on messaging for thefirst or second user based on the reports.

Thus, the processes described herein may be used to directly identify avehicle through directional wireless communication and additionalcaptured data. A token stored in a device may be retrieved by a deviceof another user that observes an issue with the vehicle, and may be usedfor anonymous communication. Utilizing data processing for data capturedby the device, the specific token for the vehicle may be determined evenwhere multiple tokens may be accessible. This allows for instantaneousdirect communication with the device for the vehicle operator whilemaintaining anonymous communications preventing identification ofunknown entities and devices. Additionally, a service provider maymaintain device anonymity and provide data processing to preventunwanted communications.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing the processes described herein, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 includes a user device 110, a vehicle device 130, and aservice provider server 140 in communication over a network 150. Userdevice 110 may be utilized by a user to capture data from vehicle device130 and/or another device associated with a vehicle in order to messagevehicle device 130 about an pending issue with the vehicle. User device110 may retrieve a token for vehicle device 130, which may allow userdevice 110 and vehicle device 130 top communicate anonymously. Userdevice 110 may capture additional information that may be used by userdevice 110 and/or service provider server 140 for the identification ofthe token for vehicle device 130. Additionally, service provider server140 may also be used for communication services, transaction processing,and message processing.

User device 110, vehicle device 130, and service provider server 140 mayeach include one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 150.

User device 110 may be implemented as a communication device that mayutilize appropriate hardware and software configured for wired and/orwireless communication with vehicle device 130 and/or service providerserver 140. For example, in one embodiment, user device 110 may beimplemented as a personal computer (PC), a smart phone, laptop/tabletcomputer, wristwatch with appropriate computer hardware resources,eyeglasses with appropriate computer hardware (e.g. GOOGLE GLASS C)),other type of wearable computing device, implantable communicationdevices, and/or other types of computing devices capable of transmittingand/or receiving data, such as an IPAD® from APPLE®. User device 110 mayalso include or correspond to a device for a vehicle, including aself-driving vehicle operational system, a vehicle console device, acomputing system managing a heads-up-display for a vehicle, or otherdevice connected to or included with a vehicle. Although a communicationdevice is shown, the communication device may be managed or controlledby any suitable processing device. Although only one communicationdevice is shown, a plurality of communication devices may functionsimilarly.

User device 110 of FIG. 1 contains a vehicle identification application120, data detection components 112, other applications 114, a database116, and a communication module 118. Vehicle identification application120 and other applications 114 may correspond to executable processes,procedures, and/or applications with associated hardware. In otherembodiments, user device 110 may include additional or different moduleshaving specialized hardware and/or software as required.

Vehicle identification application 120 may correspond to one or moreprocesses to execute modules and associated software/hardware of userdevice 110 to determine an identification of a vehicle associated withvehicle device 130 using wireless signaling and other data captured byuser device 110, and transmit a message to vehicle device 130 based on avehicle condition observed by a user associated with user device 110. Inthis regard, vehicle identification application 120 may correspond tospecialized software utilized by user device 110 to first establish awireless communication channel with vehicle device 130 and/or anotherdevice associated with a vehicle for the exchange of information,including the retrieval of digital token stored on the device. Thedigital token may allow for communication between user device 110 andvehicle device 130, which may further be anonymous to protect theparties privacy based on privacy settings. Vehicle identificationapplication 120 may utilize communication module 118 to provide wirelesscommunications with the device having the token, which may bedirectional and configured to communicate with devices in a specificdirection in which a component of user device 110 is pointed. Onceconnected with the device, vehicle identification application 120 mayretrieve the token.

Vehicle identification application 120 may capture multiple tokens, andrequire vehicle identification to communicate with vehicle device 130.Thus, vehicle identification application 120 may capture additionalinformation using data detection components 112, such as a location,images of the vehicle, a navigational direction or orientation of userdevice 110, and/or voice data. Vehicle identification application 120may utilize the tokens and additional data to identify the vehicle andthus the correct token for the vehicle. For example, the additional datamay be used to identify a vehicle (e.g., through an image of a “whitevan” and/or word analysis of voice data), and data for the token may beassociated with the vehicle (e.g., a “white van” descriptor with thetoken). In other embodiments, service provider server 104 may providesuch processing. Vehicle identification application 120 may the use thetoken to communicate with vehicle device 130, including transmission ofa message.

Vehicle identification application 120 may further utilize one or moresensors to detect an issue with the vehicle associated with vehicledevice 130 without requiring user input or action. For example, vehicleidentification application 120 may correspond to one or moreapplications or processes used by a self-driving vehicle in order tooperate the self-driving vehicle. During self-driving operations,vehicle identification application 120 may detect an issue in a nearbyin-use or parked vehicle, such as an open window, door, or gas tank thatmay present an issue, a vehicle operational hazard (e.g., a flat tire),or a usage problem (e.g., swerving). Vehicle identification application120 may utilize the aforementioned processes to identify the vehiclebased on the detected vehicle condition and vehicle information, and mayoutput a warning of the issue to an owner/operator of the self-drivingvehicle. With the warning, vehicle identification application 120 mayallow the owner/operator of the self-driving vehicle to utilize vehicleidentification application 120 and the determined identifier in order tocontact vehicle device 130. A message transmitted by vehicleidentification application 120 to vehicle device 130 may include awarning or alert of the issue. Vehicle identification application 120may also or instead contact another authority with identification of thevehicle and issue (e.g., the police if the vehicle is driving unsafelyor is left with an unsafe condition, such as open windows when parked).

Vehicle identification application 120 may be used to opt-in tomessaging services based on vehicle identification and conditionsdetected by other users (e.g., observers). When opting-in, vehicleidentification application 120 may be used to establish messaging andprivacy settings, which may indicate what messages are accepted tosend/receive, and whether the communications are anonymous or who mayreceive identification information of the user associated with userdevice 110. Vehicle identification application 120 and/or serviceprovider server 140 may analyze a message input by the user associatedwith user device 110 for vehicle device 130, and may determine whetherto transmit the message based on preferences or settings. Additionally,vehicle identification application 120 may be used to receive feedback,such as approvals or “likes” from other users based on messages, reportsor warnings based on unsolicited or harassing messages, and/or systemrestrictions based on unwanted messaging.

Vehicle identification application 120 may also allow a user to processtransactions for the vehicle associated with vehicle device 130, forexample, to provide compensation for required vehicle services when theoperator of the vehicle is absent. Thus, vehicle identificationapplication 120 may utilize a personal account accessible throughvehicle identification application 120 to initiate, receive, and/orprocess/complete transactions using services using service providerserver 140. Where the account established by vehicle identificationapplication 120 corresponds to a private or personal account for a user,vehicle identification application 120 may be implemented as a userinterface enabling the user to enter payment instruments for use in adigital wallet that provides transaction processing services. Vehicleidentification application 120 may be utilized to select paymentinstrument(s) for use during a transaction between the user and anotherentity. Vehicle identification application 120 may utilize the digitalwallet and/or user financial information for the personal account, suchas a credit card, bank account, or other financial account, as a paymentinstrument when processing a transaction and/or transferring funds.Vehicle identification application 120 may be utilized to view theresults of the transaction and/or for viewing and storage of atransaction history, such as a receipt.

Data detection components 112 correspond to a hardware and/or softwarefeature of user device 110 that assists in capturing data associatedwith a vehicle for use in determining a specific vehicle duringmulti-vehicle presence, and therefore determine a vehicle token for usein communicating with a device for the vehicle (e.g., vehicle device130). In certain embodiments, data detection components 112 may includea location detection component capable of detecting a location of userdevice 110, for example, through a GPS locator and service,triangulation process, mapping application, check-in process/feature,wireless communications, or other location detection process. Datadetection components 112 may be used to determine a location of userdevice 110, which may be utilized to determine nearby vehicles anddevices having vehicle tokens. Moreover, the location for user device110 that may be determined by data detection components 112 may beshared with, provided to, or utilized by service provider server 140when determining vehicle device 130 for communication with user device110 and/or message information for vehicle device 130.

In various embodiments, data detection components 112 may include acamera, which corresponds to an optical device of user device 110enabling user device 110 to capture or record images, including stilland/or video images. Data detection components 112 may correspond to adigital camera on user device 110 (e.g., incorporated in user device 110such as a mobile phone's digital camera in a traditional cameraorientation and/or a forward facing camera orientation that captures oneor more users as they use and view a display screen of user device 110)or associated with user device 110 (e.g., connected to user device 110but not incorporated within a body or structure of user device 110), ormay more generally correspond to any device capable of capturing orrecording an image, video, or other digital media data, includinginfrared imaging or other types imaging devices. As a digital camera,data detection components 112 may include a sensor array disposed on asemiconductor substrate having a plurality of photosensitive elementsconfigured to detect incoming light. In other embodiments, other typesof electromagnetic radiation sensors may be used, including infraredsensitive sensors/elements and the like. A camera of data detectioncomponents 112 may include various features, such as zoom, flash, focuscorrection, shutter speed controls, or other various features usable tocapture one or more images or videos of the user and/or other users orobjects.

Data detection components 112 may include other media capturecomponents, including a microphone to capture audio data. A microphoneof data detection components 112 may be used to capture voice data,which may be processed to determine particular vehicle identifyinginformation, such as vehicle descriptors (e.g., name, make. model,color, type, etc.) and/or license plate numbers. Such data may becompared to camera images to determine a specific vehicle of interestand therefore retrieve and utilize that vehicle's digital token. Datadetection components 112 may further include a navigational componentand/or application, such as a compass, as well as a gyroscope,accelerometer, or other component that may detect an orientation of userdevice 110 to determine a specific direction that user device 110 isbeing pointed in, and a vehicle and/or device having a vehicle token inthat incident direction. Data detection components 112 may also includeor be connected to components and sensors utilized with self-drivingvehicles, such as cameras used to capture views around a vehicle andused to operate the vehicle, speed sensors, distance sensors, and othercomponents.

Data detection components 112 may include peripherals and/or attachabledevices that may be connected through one or more ports orwired/wireless connections and used to capture data for determination ofa specific vehicle for retrieval of the vehicle's token andcommunication with vehicle device 130. For example, data detectioncomponents 112 may include or be associated with attachable dashboardcameras, speed detection components relative to user device 110 and/orvehicle, distance sensors, and/or connectable mobile devices. Datadetection components 112 may also include software components that mayinteract with the hardware components to facilitate data determination,such as camera controllers and processes to determine an RSSI forvehicle location determination.

In various embodiments, user device 110 includes other applications 114as may be desired in particular embodiments to provide features to userdevice 110. For example, other applications 114 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 150, or othertypes of applications. Other applications 114 may also include email,texting, voice and IM applications that allow a user to send and receiveemails, calls, texts, and other notifications through network 150,including messaging utilized by vehicle identification application 120.In various embodiments, other applications 114 may include financialapplications, such as banking applications and/or transaction processingapplication that may be utilized by vehicle identification application120 during transaction processing for a service utilized by a vehicleassociated with vehicle device 130. Other applications 114 may alsoinclude other location detection applications, which may be used todetermine a location for user device 110, such as a mapping application.Other applications 114 may include device interface applications andother display modules that may receive input from the user and/or outputinformation to the user. For example, other applications 114 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI) configured to provide an interface to the user. Otherapplications 114 may therefore use components of user device 110, suchas display components capable of displaying information to users andother output components, including speakers.

User device 110 may further include database 116 stored on a transitoryand/or non-transitory memory of user device 110, which may store variousapplications and data and be utilized during execution of variousmodules of user device 110. Database 116 may include, for example,identifiers such as operating system registry entries, cookiesassociated with vehicle identification application 120 and/or otherapplications 114, identifiers associated with hardware of user device110, or other appropriate identifiers, such as identifiers used forpayment/user/device authentication or identification, which may becommunicated as identifying the user/user device 110 to vehicle device130 and/or service provider server 140. Moreover, received identifiersmay be stored in database 116 with other data detected by user device110 that may allow identification of a vehicle associated with vehicledevice 130. Such data may also include messages and other content totransmit to vehicle device 130.

User device 110 includes at least one communication module 118 adaptedto communicate with vehicle device 130, service provider server 140,and/or another nearby device within range of communication module 118.In various embodiments, communication module 118 may include a DSL(e.g., Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency, infrared,Bluetooth, and near field communication devices. Communication module118 may communicate directly with nearby devices using wirelesscommunications, such as Bluetooth Low Energy, LTE Direct, WiFi, radiofrequency, infrared, Bluetooth, and near field communications, forexample, to detect nearby devices and/or request data from nearbydevices, such as a digital token used for vehicle identification.Additionally, communication module 118 may provide directional wirelesscommunication capabilities, such as signal beam that may be directed ata particular device or in a particular direction.

Vehicle device 130 may be implemented as a communication device that mayutilize appropriate hardware and software configured for wired and/orwireless communication with user device 110 and/or service providerserver 140. For example, in one embodiment, vehicle device 130 may beimplemented as a console device or onboard computing device withinvehicle device 130. Vehicle device 130 may also correspond to a deviceused by a user inside a vehicle or associated with a vehicle (e.g., auser that is remote from the vehicle but may receive messages based on acondition of the vehicle), such as a personal computer (PC), telephonicdevice, a smart phone, laptop/tablet computer, wristwatch withappropriate computer hardware resources, eyeglasses with appropriatecomputer hardware (e.g. GOOGLE GLASS C)), other type of wearablecomputing device, implantable communication devices, and/or other typesof computing devices capable of transmitting and/or receiving data.Although only one device is shown, a plurality of devices may functionsimilarly.

Vehicle device 130 of FIG. 1 contains a communication application 132,other applications 134, a database 136, and a communication module 138.Communication application 132 and other applications 134 may correspondto executable processes, procedures, and/or applications with associatedhardware. In other embodiments, vehicle device 130 may includeadditional or different modules having specialized hardware and/orsoftware as required.

Communication application 132 may correspond to one or more processes toexecute software of vehicle device 130 to receive communications fromuser device 110 and respond to the communications. In certainembodiments, communication application 132 may also be utilized inconjunction with database 136 and communication module 138 to provide adigital token identifying a vehicle and vehicle device 130 forcommunications based on a condition of the vehicle. However, in otherembodiments, another device or vehicle component may be configured toprovide such data in response to a query from user device 110, such as abeacon or dongle attached to or included within a vehicle, a wirelessautomated system for the vehicle (e.g., a wireless door locking system),a smart car component, or other on-board device or component for avehicle. After determination of vehicle device 130 by user device 110and/or service provider server 140 for the receipt of messages,communication application 132 may receive such messages concerning anissue of condition of the vehicle associated with vehicle device 130.

In this regard, communication application 132 may correspond tospecialized hardware and/or software utilized by vehicle device 130 tooutput messages through one or more application interfaces using agraphical user interface (GUI) of vehicle device 130. Communicationapplication 132 may receive a message based on the vehicle and outputthe message. In certain embodiments, communication application 132 mayinclude privacy and messaging preferences to determine whether to outputthe message based on the message content, which may include processes todetermine message content (e.g., keyword search/analysis, imagerecognition, etc.). Communication application 132 may further receiveinput for feedback back to user device 110, such as a reply message,thanks or “like,” report or dislike,” a reimbursement for a processedtransaction, or other message. Communication application 132 may also beused to report user device 110 and/or a user to service provider server140, for example, based on unwanted messages, and may also be used tosee a rating for vehicle device 130 and/or the operator associated withvehicle device 130 based on responses by other users.

In various embodiments, vehicle device 130 includes other applications134 as may be desired in particular embodiments to provide features tovehicle device 130. For example, other applications 134 may includesecurity applications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 150, or othertypes of applications. Other applications 134 may also include email,texting, voice and IM applications that allow a user to send and receiveemails, calls, texts, and other notifications through network 150, whichmay be utilized with communication applicant 132 where necessary. Invarious embodiments, other applications 134 may include financialapplications, such as banking applications and electronic transactionprocessing applications to provide reimbursement for transactionsprocessed by user device 110. Other applications 134 may also includeother location detection applications, which may be used to determine alocation for the user, such as a mapping, compass, and/or GPSapplication, which can include a specialized GPS receiver that obtainslocation information for vehicle device 130 and determines whethervehicle device 130 is nearby a vehicle. Such information may be providedto user device 110 and/or service provider server 140 for a response toa message. Other applications 134 may include device interfaceapplications and other display modules that may receive input from theuser and/or output information to the user. For example, otherapplications 134 may contain software programs, executable by aprocessor, including a graphical user interface (GUI) configured toprovide an interface to the user. Other applications 134 may thereforeuse devices of vehicle device 130, such as display devices capable ofdisplaying information to users and other output devices, includingspeakers.

Vehicle device 130 may further include database 136 stored in atransitory and/or non-transitory memory of vehicle device 130, which maystore various applications and data and be utilized during execution ofvarious modules of vehicle device 130. Database 136 may include, forexample, identifiers such as operating system registry entries, cookiesassociated with communication application 132 and/or other applications134, identifiers associated with hardware of vehicle device 130, orother appropriate identifiers, such as identifiers used forpayment/user/device authentication or identification, which may becommunicated as identifying vehicle device 130 to user device 110 and/orservice provider server 140, such as a digital token that allows forcommunication with vehicle device 130. In various embodiments, database136 may also store received messages.

Vehicle device 130 includes at least one communication module 138adapted to communicate with user device 110 and/or service providerserver 140. In various embodiments, communication module 138 may includea DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public SwitchedTelephone Network) modem, an Ethernet device, a broadband device, asatellite device and/or various other types of wired and/or wirelessnetwork communication devices including microwave, radio frequency,infrared, Bluetooth, and near field communication devices. Communicationmodule 138 may communicate directly with nearby devices using wirelesscommunications, such as Bluetooth Low Energy, LTE Direct, WiFi, radiofrequency, infrared, Bluetooth, and near field communications.

Service provider server 140 may be maintained, for example, by an onlineservice provider, which may provide routing information to user device110 for connection with vehicle device 130. In this regard, serviceprovider server 140 includes one or more processing applications whichmay be configured to interact with user device 110, vehicle device 130,and/or another device/server to facilitate communications andtransactions between users based on data captured by one of the user. Inone example, service provider server 140 may be provided by PAYPAL®,Inc. of San Jose, CA, USA. However, in other embodiments, serviceprovider server 140 may be maintained by or include another type ofservice provider, which may provide connection services to a pluralityof users.

Service provider server 140 of FIG. 1 includes a service providerapplication 142, other applications 144, a database 146, and a networkinterface component 148. Service provider application 142 and otherapplications 144 may correspond to executable processes, procedures,and/or applications with associated hardware. In other embodiments,service provider server 140 may include additional or different moduleshaving specialized hardware and/or software as required.

Service provider application 142 may correspond to one or more processesto execute modules and associated specialized hardware of serviceprovider server 140 to provide a service to user device 110, which maybe accessed through one or more applications of user device 110, forexample, vehicle identification and communication processing services.In this regard, service provider application 142 may correspond tospecialized hardware and/or software to receive an identificationrequest of a vehicle and determination of a digital identity token forthe vehicle based on received token(s) and additional data of thevehicle, such as captured images, voice data, directional or deviceorientation information, and/or a location or direction of travel.Service provider application 142 may process the additional data toidentify a vehicle that user device 110 is targeting for communication,and identify one of the tokens based on additional vehicle descriptorsassociated with the token (e.g., contained within the token orretrievable using the token). Service provider application 142 mayprovide the selected token to user device 110 for confirmation withvehicle information and communication with vehicle device 130, and/ormay utilize the token to route messages from user device 110 to vehicledevice 130. Additionally, service provider application 142 may utilizemessaging and privacy settings to determine whether to send messagesbetween user device 110 and vehicle device 130, as well as what identityinformation to reveal to user device 110 and vehicle device 130. Inother embodiments, user device 110 may provide such processing.

In certain embodiments, service provider application 142 may be used toreceive and/or transmit information for processing and completing of oneor more transactions paid for by an account associated with user device110 for a vehicle associated with vehicle device 130, as well as processreimbursements to the account. The user associated with user device 110may establish a payment account with service provider application 142 byproviding personal and/or financial information to service providerserver 140 and selecting authentication credentials. In variousembodiments, the financial information may include payment instrumentinformation, such as account numbers. The account may be used to sendand receive payments. The payment account may be accessed and/or usedthrough a browser application and/or dedicated payment applicationexecuted by user device 110. Service provider application 142 mayreceive a payment request from user device 110 for a transaction by theaccount to a service provider providing a vehicle service (e.g.,parking, tolls, etc.) to the vehicle, which may include identifiers,tokens, or other data used for transaction processing. Service providerapplication 142 may process a payment, and may provide a transactionhistory to user device 110 and/or vehicle device 130.

In various embodiments, service provider server 140 includes otherapplications 144 as may be desired in particular embodiments to providefeatures to service provider server 140. For example, other applications144 may include security applications for implementing server-sidesecurity features, programmatic client applications for interfacing withappropriate application programming interfaces (APIs) over network 150,or other types of applications. Other applications 144 may containsoftware programs, executable by a processor, including a graphical userinterface (GUI), configured to provide an interface to the user whenaccessing service provider server 140, where the user or other users mayinteract with the GUI to more easily view and communicate information.In various embodiments, other applications 144 may include additionalconnection and/or communication applications, which may be utilized tocommunicate information to over network 150.

Additionally, service provider server 140 includes database 146.Database 146 may store various identifiers associated with user device110 and/or vehicle device 130. Database 146 may also store account data,including payment instruments and authentication credentials, as well astransaction processing histories and data for processed transactions.Database 146 may store received digital tokens for vehiclecommunications and additional data for selected vehicles that usersrequest identification of for the communications. Additionally, database146 may store opt-in preferences and privacy/messaging settings withexchanges messages between devices.

In various embodiments, service provider server 140 includes at leastone network interface component 148 adapted to communicate user device110 and/or vehicle device 130 over network 150. In various embodiments,network interface component 148 may comprise a DSL (e.g., DigitalSubscriber Line) modem, a PSTN (Public Switched Telephone Network)modem, an Ethernet device, a broadband device, a satellite device and/orvarious other types of wired and/or wireless network communicationdevices including microwave, radio frequency (RF), and infrared (IR)communication devices.

Network 150 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 150 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 150 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2A is an exemplary real-world environment for directional wirelesscommunication for vehicle identification and device communication,according to an embodiment. Environment 200 a of FIG. 2A includes userdevice 110 and vehicle device 130, discussed in reference to system 100of FIG. 1 . In this regard, user device 110 is associated with a user102 observing an issue with a vehicle 1002 that is associated withvehicle device 130 to provide a digital token and/or display messagesfrom user device 110.

In order to provide communications between two devices unknown to eachother, such as user device 110 and vehicle device 130, wirelesscommunications may be used to retrieve an identifier that allows forcommunications (which may or may not be anonymous) between devices. Inthis regard, user 102 may utilize user device 110 to exchange signalingwith vehicle device 130 at a location 1000 to retrieve the identifier ortoken stored to vehicle device 130 when user 102 observes an issue withvehicle 1002 at location 1000. User 102 may “point” or direct userdevice 110 toward vehicle 1002 as shown in environment 200 a, wherecommunication module 118 may emit a directional wireless communicationsignal 1012 that establishes a communication pathway with vehicle device130 and retrieves the token from vehicle device 130. Directionalwireless communication signal 1012 may query vehicle device 130 for thetoken, for example, using an established protocol, query, and/oridentification/authentication mechanism utilized by the system forcommunications with vehicle device 130. In various embodiments, userdevice 110 may capture further information as user device 110 isdirected at vehicle 1002, such as an image, voice data, and/or anorientation of user device 110.

After retrieval, this token may then be processed by user device 110 todetermine vehicle device 130 for communication regarding vehicle 1002.User device 110 may display an interface 1004, where interface 1004 maydisplay information identifying vehicle 1002 (e.g., an image, licenseplate, description, etc.). Interface 1004 may also be used to submit arequest 1006 for communication with vehicle device 130, which mayinclude the retrieved token 1008 for communication with vehicle device130 and a message 1010. Message 1010 may then be sent to vehicle device130 using token 1008, which may be pre-processed to determine messagecontent and appropriateness for delivery.

FIG. 2B is an exemplary real-world environment for vehicleidentification and device communication where multiple vehicles areoperating in close proximity, according to an embodiment. Environment200 b of FIG. 2B includes user device 110, discussed in reference tosystem 100 of FIG. 1 . Environment 200 b further includes a vehicledevice 130 a, a vehicle device 130 b, a vehicle device 130 c, a vehicledevice 130 d, and a vehicle device 130 e all corresponding generally tothe features and processes executed by vehicle device 130 discussed inreference to system 100 of FIG. 1 . In this regard, user device 110 maybe located in a vehicle 1004 and may be surrounded by a vehicle 1002 a,a vehicle 1002 b, a vehicle 1002 c, a vehicle 1002 d, and a vehicle 1002e each having one of vehicle devices 130 a-e. User device 110 may betargeting vehicle device 130 a in vehicle 1002 a for communicationsregarding an observed issue or condition of vehicle 1002 a.

In environment 200 b, a location 1100 includes multiple vehicles 1002a-e where user device 110 requires identification of vehicle 1002 a fromvehicles 1002 a-e, where all of vehicle devices 130 a-e may providetheir respective vehicle identification token to user device 110. Inorder to identify vehicle device 130 a for vehicle 1002 a that userdevice 110 is attempted to retrieve a token and communicate with, userdevice 110 may determine additional information. For example, a locationof user device 110 may be determined, for example, using a GPS locatoror other device. A geofence 1102 may then be established around userdevice 110 that may eliminate vehicle device 130 d and 130 e from beingconsidered even if their tokens are retrievable based on being outsideof geofence 1102. Further, a boundary 1104 may separate vehicle 1004 foruser device 110 from vehicle 1002 e for vehicle device 130 e becausethey are travelling in opposite directions. Thus, due to the directionof travel, vehicle device 130 e may also be eliminated as correspondingto vehicle device 130 a that user device 110 is attempting to contact.

Additionally, directional data acquisition 1106 may capture direct dataof vehicle 1002 a corresponding to vehicle device 130 a foridentification of the token for vehicle device 130 a. For example,directional data acquisition 1106 may include visual data capture,directional wireless signaling, and/or an orientation or direction ofuser device 110. Visual data capture by user device 110 may correspondto an image of vehicle 1002 a, which may include a color, make, model,license plate number, or other identifying characteristic of vehicle1002 a. This data may be determined through image recognition processesand other image processing to identify specific visual data for vehicle1002 a. User device 110 may then process the determined visual data withtoken information that may identify visual characteristics of vehicle1002 a, such as the color, make, model, license plate number, etc.

In other embodiments, directional data acquisition 1106 may correspondto a directional wireless signal that is used to only capture the tokenfor vehicle device 130 a, such as line-of-sight directional wirelesssignaling. However, where the wireless signaling may be radiateduniformly around user device 110, a compass or orientation detectioncomponent (e.g., gyroscope or accelerometer) may determine anorientation of user device 110. An orientation may correspond to adirection that user device 110 is pointed in, which may be utilized toidentify vehicle 1002 a from vehicles 1002 a-e. The orientation may beprocessed with geo-location data for vehicle 1002 a, which may beprovided with the token for vehicle device 130 a and compared togeo-location data 110. This may allow identification of vehicle 1002 a.The orientation may also be used with image data that may capturevehicles 1002 b and 1002 c within the image. The orientation may be usedto identify vehicle 1002 a based on the orientation of user device 110and vehicles 1002 a-c in the image. Thus, additional data captured byuser device 110 may be used to identify vehicle 1002 a and thuseliminate tokens for vehicle devices 130 b and 130 c from being utilizedfor communication. User device 110 may then communicate with vehicledevice 130 a based on the selected token.

FIG. 3A is a flowchart of an exemplary process executed by a serviceprovider for vehicle identification and device communication, accordingto an embodiment. Flowchart 300 a includes an exemplary process by aservice provider for communication between a user device of a userobserving a vehicle and a device associated with that vehicle. Note thatone or more steps, processes, and methods described herein may beomitted, performed in a different sequence, or combined as desired orappropriate.

In order to initiate device communications using a token identifying aparticular vehicle, a device may initially be required to opt-in tosending and receiving communications with other devices, for example, byproviding registration information at step 2002 of service providerserver flow 2000. This may include establishment of registrationinformation, privacy settings, and messaging preferences with theservice provider for use of the service provider's messaging service.Additionally, this may cause generation of the vehicle's messagingidentification token and establishment of that token on a device. Atstep 2004 of service provider server flow 2000, an identificationrequest is received from a device for a vehicle, which may includeidentification of at least one token and additional data captured of thevehicle for identification of the specific vehicle and associated token.These steps may be performed by the service provider so that the serviceprovider may determine the token used for messaging with the vehicle'sdevice.

At step 2006 of service provider server flow 2000, an anonymity statusmay be determined for the vehicle, which may determine whatidentification data is shown to other devices when messaging thevehicle's device. Based on the anonymity status, the user's device thatcaptures the token and data may be notified of whether messaging isaccepted by the vehicle's device, as well as what messaging may beaccepted, at step 2008 of service provider server flow 2000. At step2010 of service provider server flow 2000, the service provider may thenreceive a message from the user's device for the vehicle, which may beoutput through the device associated with the vehicle. Thus, thevehicle's device is notified of the message and any additional datacaptured by the user's device that observes the vehicle based on theanonymity status, at step 2012 of service provider server flow 2000.

FIG. 3B is a flowchart of an exemplary process executed by a device forvehicle identification and device communication, according to anembodiment. Flowchart 300 b includes an exemplary process by a serviceprovider for communication between a user device of a user observing avehicle and a device associated with that vehicle. Note that one or moresteps, processes, and methods described herein may be omitted, performedin a different sequence, or combined as desired or appropriate.

In various embodiments, device-to-device communications may be performedwithout the use of a service provider for device notifications of avehicle condition from another device. At step 2102 of device-to-deviceflow 2100, a first device may determine an identity token for a vehiclethrough wireless communications and analysis of additional data capturedfor the vehicle, such as voice data, images, and/or other data. Thefirst device may the determine an opt-in status using the identitytoken, which may include whether the vehicle is opted-in to receivingcommunications from the first device, at step 2104 of device-to-deviceflow 2100. The status may also determine the communication and privacypreferences for messaging a second device associated with the vehicle.

Based on the opt-in status, a message may be processed with a seconddevice using the identity token and the restrictions and preferences forthe opt-in status, at step 2106 of device-to-device flow 2100. This mayinclude sending the message, redacting or eliminating unwantedinformation, or refusing to send the message based on the messagecontent. Additionally, the message may be processed to retain anonymityof the parties in the transmission. At step 2108 of device-to-deviceflow 2100, a response to the message may be received and may be outputto on the first device.

FIG. 4 is a flowchart of an exemplary process for vehicle identificationand device communication through directional wireless signaling,according to an embodiment. Note that one or more steps, processes, andmethods described herein may be omitted, performed in a differentsequence, or combined as desired or appropriate.

At step 402 of flowchart 400, an identity token for a vehicle isreceived from a first device over a network through wirelesscommunications between the first device and a second device associatedwith the vehicle. The first device may include a wireless transceiverfor wireless communications, and the identity token may be received bythe first device based on an identification request transmitted by thefirst device to a vehicle device, such as the second device or anon-board vehicle console device of the vehicle. The wireless transceivermay comprise one of a directional Bluetooth transceiver or a directionalcolorless laser transceiver, and the wireless signaling may establish adirect wireless link between the first device and the vehicle device.The token may uniquely identify the vehicle to a service providerreceiving the token. The token may be sent by the vehicle device to thefirst device through wireless signaling and may, in certain embodiments,include a communication acceptance status for the vehicle. However, thecommunication acceptance status or other privacy preference may also bedetermined by the service provider using the token.

Prior to receiving the token, a user associated with the first devicemay provide an opt-in setting to a vehicle identification system for thefirst device, which may comprise privacy settings by the user with thevehicle identification system. Thus, an application on the first devicemay be configured to detect identity tokens from other devices forvehicles through the first device's wireless transceiver. Thecommunication acceptance status and the privacy settings may include ananonymity setting. Additionally, the token may comprise a randomizedtoken that prevents identification of a user associated with the vehicleand/or vehicle device.

In certain embodiments, a plurality of tokens may be detected by thefirst device, and an identification of the specific vehicle and devicemay be determined using at least one of a GPS location, a directionalcomponent of the wireless transceiver, a directional or orientationdetection component of the first device, a user profile associated withthe first device, voice data provided by the user to the first device,or an image captured by the mobile device. For example, an image mayinclude an image of a license plate of the vehicle, a color of thevehicle, a name of the vehicle, a make of the vehicle, or a model of thevehicle. Other additional indicators of the vehicle may include adirection of travel associated with the first device, additionalvehicles within a geo-fence around the vehicle, a direction of travel ofthe additional vehicles within the geo-fence, locations of theadditional vehicles, a voice command recorded by the first device, or apolar orientation detected by a compass application of the first device.Thus, additional data detected by the first device may be received andused to determine the vehicle and thus the vehicle's identity token.

At step 404 of flowchart 400, a privacy preference for the vehicle isdetermined using the identity token. The privacy preference istransmitted to the first device over the network, at step 406 offlowchart 400. At step 408 of flowchart 400, a messaging requestassociated with the vehicle from the first device is processed based onthe privacy preference. For example, the communication acceptance statusor privacy preference may comprise a first opt-in setting by the vehicledevice to receive communications from other devices, and the firstdevice or the service provider may transmit a message to the vehicledevice using the token. The processing may also include processing atransaction for the vehicle based on a location of the vehicle andtransmitting a message associated with the transaction to one of thevehicle device based on the communication acceptance status or a serviceprovider associated with the token. In further embodiments, a locationof the vehicle may be determined using the first device, and anemergency notification may be transmitted to an additional devicelocated within a geo-fence for the location.

The processing may also include receiving a message from the firstdevice, wherein the message comprises identification of a vehicle issueassociated with the vehicle. A service provider may then determinewhether the vehicle issue is resolved using one of the second device oran on-board smart vehicle device of the vehicle and process the messagebased on the determining whether the vehicle issue is resolved. Theprocessing the messaging request may also comprise transmitting amessaging identifier for the second device to the first device, whereinthe messaging identifier allows for communications from the first deviceto the second device based on the privacy settings or preferences.However, where the processing comprises receiving a message, the serviceprovider or an application on the first device may determine whether tosend the message based on message content for the message. For example,text analysis may be performed on the message content, and it may bedetermined whether the message comprises one of an advertisement, athreat, or a spam message. This may also be determined using an accountstatus, which may flag the account as abusive. If so the message may beblocked.

FIG. 5 is a block diagram of a computer system suitable for implementingone or more components in FIG. 1 , according to an embodiment. Invarious embodiments, the communication device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, a wearable computing device such as glasses or awatch, Bluetooth device, key FOB, badge, etc.) capable of communicatingwith the network. The service provider may utilize a network computingdevice (e.g., a network server) capable of communicating with thenetwork. It should be appreciated that each of the devices utilized byusers and service providers may be implemented as computer system 500 ina manner as follows.

Computer system 500 includes a bus 502 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 500. Components include aninput/output (I/O) component 504 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 502. I/O component 504 may also include anoutput component, such as a display 511 and a cursor control 513 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 505 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component505 may allow the user to hear audio. A transceiver or network interface506 transmits and receives signals between computer system 500 and otherdevices, such as another communication device, service device, or aservice provider server via network 150. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 512, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 500 or transmission to other devices via a communicationlink 518. Processor(s) 512 may also control transmission of information,such as cookies or IP addresses, to other devices.

Components of computer system 500 also include a system memory component514 (e.g., RAM), a static storage component 516 (e.g., ROM), and/or adisk drive 517. Computer system 500 performs specific operations byprocessor(s) 512 and other components by executing one or more sequencesof instructions contained in system memory component 514. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor(s) 512 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious embodiments, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 514, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 502. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 500. In various other embodiments of thepresent disclosure, a plurality of computer systems 500 coupled bycommunication link 518 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

1. (canceled)
 2. A method, comprising: receiving, by a vehicle device for a vehicle of a user using a wireless communication system for the vehicle, an identity token for a first entity that is different from the vehicle and the user; generating, by the vehicle device, a transaction associated with the first entity based on the identity token, wherein the transaction is processable by a transaction processor using a digital token accessible by the vehicle device; generating, by the vehicle device, a digital message for the first entity based on the transaction, wherein the digital message includes the digital token usable to process the transaction; and transmitting, by the vehicle device using the wireless communication system and the identity token, the digital message over short-range wireless communications.
 3. The method of claim 2, wherein the transaction comprises a payment to the first entity for a product available from the first entity, and wherein the operations further comprise: receiving a confirmation of the payment made to the first entity; and displaying the confirmation to the user using a display component of the vehicle device.
 4. The method of claim 2, wherein the transaction comprises a payment to a second entity on behalf of the first entity, and wherein the transmitting the digital message comprises initiating the payment with a computing system associated with the second entity for processing the transaction for the first entity using the digital token and the transaction processor.
 5. The method of claim 4, further comprising: requesting, from the first entity via the transaction processor, a reimbursement for the payment on behalf of the first entity, wherein the reimbursement identifies the first entity using the identity token.
 6. The method of claim 2, wherein the transaction comprises one of a toll road payment, a parking fee, an item purchase from the first entity, or a service purchase from the first entity.
 7. The method of claim 2, wherein prior to the determining the transaction, the method further comprises: determining a privacy preference of the first entity based on the identity token, wherein the privacy preference specifies at least one restriction on an identity, a time, or a reason for contacting the first entity using the identity token, wherein the transmitting the digital message is performed in compliance with the privacy preference.
 8. The method of claim 7, wherein the privacy preference further specifies that the entity may be contacted regarding a payment to be made to the first entity for the transaction or a payment required by the first entity for the transaction.
 9. The method of claim 2, wherein the digital token is accessible from a digital wallet utilized in an application on the vehicle device, and wherein the vehicle device comprises one of an onboard computing system of the vehicle or a mobile smart phone connectable to the onboard computing system.
 10. A vehicle device of a vehicle for a user, the vehicle device comprising: a non-transitory memory; a wireless communications unit; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the vehicle device to perform operations comprising: detecting an identity token of an entity in a proximity to the vehicle, wherein the identity token is available within the proximity and identifies the entity distinct from the user and the vehicle; generating a transaction with the entity based on the identity token; requesting, from a transaction processor, a payment token that is designated for the entity and usable by the entity to process the transaction with the transaction processor; receiving the payment token from the transaction processor; and transmitting, using the wireless communications unit and the identity token, a message including the payment token to the entity.
 11. The vehicle device of claim 10, wherein the operations further comprise: receiving a result of the transaction processor processing the transaction using the identity token and the payment token; and displaying, using a display connected with the vehicle device, the result during an operation of the vehicle by the user.
 12. The vehicle device of claim 10, wherein the payment token is generated using a digital wallet of the user with the transaction processor.
 13. The vehicle device of claim 12, wherein the digital wallet is associated with a plurality of payment instruments of the user, and wherein the digital token corresponds to one of the plurality of payment instruments selected for the digital token based on at least one of a user preference of the user or available balances of the plurality of payment instruments.
 14. The vehicle device of claim 10, wherein the identity token is detected during an operation of the vehicle by the user, and wherein the operations further comprise: displaying, using a display connected with the vehicle device, an identification of the entity based on the identity token.
 15. The vehicle device of claim 14, wherein the transaction comprises a payment for one of an item or a service purchase during an operation of the vehicle, fuel for the vehicle, or a toll road payment for a toll road utilized during the operation of the vehicle.
 16. The vehicle device of claim 14, wherein, prior to the generating the transaction, the operations further comprise: receiving, via an input component connected with the vehicle device, a request to generate the transaction based on the identification of the entity.
 17. The vehicle device of claim 10, wherein the requesting the payment token comprises providing an authentication credential entered by the user to one of the vehicle device or a mobile device connected with the vehicle device.
 18. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: detecting, by a vehicle device for a vehicle of a user, an identity token for an entity that is different from the vehicle and the user; determining, by the vehicle device, a transaction with the entity based on the identity token; generating, by the vehicle device, a digital message to process the transaction with the entity using a digital token associated with the user; and transmitting, by the vehicle device using a wireless communication system and the identity token, the digital message over short-range wireless communications for processing of the transaction by a transaction processor using the digital token.
 19. The non-transitory machine-readable medium of claim 18, wherein the digital message is transmitted to one of a mobile device, a point-of-sale device, or a drive-through device of the entity, and wherein the entity comprises a mobile merchant selling an item or a service to the user during an operation of the vehicle by the user.
 20. The non-transitory machine-readable medium of claim 18, wherein the operations further comprise: receiving a confirmation of a payment for the transaction; and displaying the confirmation and the payment via a display component of the vehicle device.
 21. The non-transitory machine-readable medium of claim 18, wherein the transaction comprises a payment required by the entity during an operation of the vehicle by the user. 